Current deployment setup

The .gitlab-ci.yml is configured for GitLab Pages deployment with two stages:

1. Build stage: Validates that index.html exists
2. Deploy stage: Copies files to a public/ directory for GitLab Pages

Deployment options

Option 1: GitLab Pages (current)

• Pros: Free, automatic, HTTPS, works with your current config
• Cons: URL format: https://[namespace].gitlab.io/[project-name]
• How it works: Push to main/master → pipeline runs → site deploys automatically

Option 2: Custom domain with GitLab Pages

• Use your own domain (e.g., cv.yourdomain.com)
• Requires DNS configuration
• Still uses GitLab Pages infrastructure

Option 3: Deploy to your own server

• Use the commented SSH/rsync section in the CI file
• Requires: server, SSH access, CI/CD variables for credentials
• More control, but you manage the server

Option 4: Other platforms

• Netlify, Vercel, Cloudflare Pages, etc.
• Would need a different CI/CD config

Questions

1. Do you want to use GitLab Pages, or deploy to your own server/domain?
2. Do you have a custom domain you want to use?
3. Should I update the CI/CD to remove the analytics.js reference (since we’re using the inline script now)?